When troubleshooting the cause of a Notes or Domino LotusScript hang or crash, it's useful to know what the LotusScript was doing at the time of the problem. Historically, this was accomplished by placing print statements inside of suspect code. Starting in Lotus Notes and Domino 8.5.3, NSD will ...

This document will explain how to map an AIX NSD crash stack to actual code that was a cause of the crash. It will not guarantee a root cause, but will assist in debugging your application to find the root cause. The documentation assumes you understand how to read an NSD.

This document will explain how to map a windows NSD crash stack to actual code that was a cause of the crash. It will not guarantee a root cause, but will assist in debugging your application to find the root cause. The documentation assumes you understand how to read an NSD.

The objective of this group of documentation is to show how to map an NSD crash stack to application code within an agent. This can be helpful when you are trying to debug an application but want to lower the scope of debugging to save time.